In technology, System Maintenance is the ongoing process of keeping computer systems (hardware, software, and networks) healthy, secure, and efficient.
Just like maintaining a car, a computer system requires regular check-ups, minor adjustments, and occasional part replacements to prevent breakdowns and extend its useful life.
❓ Question 1 — Which of the following is the primary goal of System Maintenance?
Not all maintenance is the same size. To understand maintenance, we first look at the magnitude of the change being made. We categorize this size into three tiers, from smallest to largest:
Patch — A tiny, surgical fix. It is a piece of code designed to fix a specific bug or close a security hole. (e.g., Fixing a typo in the code that causes the app to crash when you hit "save".)
Update — A medium, routine improvement. It often bundles several patches together and adds minor enhancements or tweaks to make the current version work better. (e.g., Releasing a monthly update for your phone's operating system that improves battery life and installs security patches.)
Upgrade — A major overhaul. This involves moving to a completely new, significantly different version of the software or replacing old hardware with new hardware. (e.g., Moving from Windows 10 to Windows 11, or swapping an old spinning hard drive for a new Solid-State Drive.)
❓ Question 2 — A software company releases a small piece of code specifically designed to close a security hole in its video editing app. This is best described as a:
This is "bug fixing." It happens when users discover errors, glitches, or security flaws in the existing system. The goal is to restore the system to its intended working state.
Typical Size/Scope: Patch. Because you are targeting a specific defect, you use a small, surgical patch to correct it without accidentally breaking something else.
❓ Question 3 — A technician is looking at a list of reported issues. Based on the definition of Corrective Maintenance, which issue should they fix first?
Technology does not exist in a vacuum. The world around a system is constantly changing — new operating systems are released, laws change, or new hardware is invented. Adaptive maintenance ensures your system continues to work within this changing environment.
Typical Size/Scope: Update or Upgrade. If a minor change in the environment occurs (e.g., a new web browser is released), an update is needed. If the environment changes drastically (e.g., the old programming language is no longer supported by modern servers), a full upgrade may be required.
❓ Question 4 — Which of the following situations describes a need for Adaptive Maintenance?
Even if a system works perfectly and fits its environment, users will always want more. Perfective maintenance involves improving performance, refining the user interface, or adding new, non-essential features to meet evolving user expectations.
Typical Size/Scope: Update or Upgrade. Adding a new "dark mode" feature or making a program load 20% faster is usually achieved through an update. Adding a massive suite of brand-new tools to the software would require an upgrade.
❓ Question 5 — A project manager is reviewing user feedback for an app that currently works fine, has no bugs, and is compatible with all current devices. Which piece of feedback would be categorized as Perfective Maintenance?
This is the most proactive type of maintenance. Instead of waiting for a system to fail, the technician looks for "silent" issues — such as slowly failing hard drives, memory leaks, or aging server fans — and fixes them before they cause downtime or data loss.
Typical Size/Scope: Patch or Update. Preventative maintenance often uses patches (e.g., applying a security patch for a vulnerability that hasn't been hacked yet) or updates (e.g., optimizing database code so it doesn't crash when it reaches high traffic next year).
❓ Question 6 — Which of the following tasks is an example of Preventative Maintenance?
Read the following real-world scenarios involving a company's Payroll Software. Identify whether the scenario is a Patch, Update, or Upgrade (Size), and whether it is Corrective, Adaptive, Perfective, or Preventative (Purpose).
Note: They are not in the same order as the lesson!
❓ Question 7 — Employees complain that the software looks old and is slow. The company buys and installs the newest version of the Payroll Software (Payroll 2.0), which has a brand-new interface and major new features. What is the Size and Purpose?
❓ Question 8 — The software vendor realizes that in Payroll 2.0, there is a flaw that could allow a hacker to steal bank account data next year. Even though no one has been hacked yet, the vendor sends out a small fix to lock down the security before it becomes a problem. What is the Size and Purpose?
❓ Question 9 — The government changes the national tax rate from 5% to 6%. The developer releases a routine package of changes for the current software version that includes the new tax tables and a few minor security patches. What is the Size and Purpose?
❓ Question 10 — The accounting team notices the software crashes if an employee has a hyphen in their last name. The developer sends a tiny fix specifically for that coding bug. What is the Size and Purpose?
❓ Question 11 — A hospital runs a software update on its patient portal to make the text easier to read and the buttons easier to click. This is a(n) ______ driven by ______ maintenance.
❓ Question 12 — Which sequence correctly orders the "Size/Scope" of changes from smallest to largest?
🎉 You've mastered System Maintenance!
Recap:
• Patch – Tiny, surgical fix
• Update – Routine, medium-sized improvement
• Upgrade – Major version overhaul
• Corrective – Fix what's broken
• Adaptive – Keep up with the environment
• Perfective – Make good things better
• Preventative – Stop problems before they happen
These concepts are how IT professionals keep the digital world running smoothly — from your smartphone to global banking systems.